User equipment (ue)

ABSTRACT

Provided are procedures for initial UE registration and periodic or movement-based registration, and a communication unit to achieve management of the maximum number of UEs connected to each slice in 5GS. Furthermore, a method for managing a timer running after completion of the registration procedure, and a method of registration procedure and a communication unit for both a UE in which the timer is running and a UE in which the timer is not running are provided, thus providing a communication unit to implement functions related to the management of the maximum number of UEs connected to each slice in 5GS.

TECHNICAL FIELD

This application relates to a User Equipment (UE). This application claims the benefit of priority to JP 2019-236466 filed on Dec. 26, 2019, which is incorporated herein by reference in its entirety.

BACKGROUND ART

The 3rd Generation Partnership Project (3GPP), which undertakes activities for standardizing recent mobile communication systems, has studied System Architecture Evolution (SAE) which is a system architecture of Long Term Evolution (LTE).

Additionally, the 3GPP has recently studied next-generation communication technologies and system architectures for a 5th Generation (5G) mobile communication system which is a next generation mobile communication system, and in particular, has standardized a 5G System (5GS) as a system for realizing a 5G mobile communication system (see NPL 1 and NPL 2). In the 5GS, technical problems attributable to connection of various terminals to a cellular network are extracted to standardize solutions.

CITATION LIST Non Patent Literature

-   NPL 1: 3GPP TS 23.501 V16.3.0 (2019 December); 3rd Generation     Partnership Project; Technical Specification Group Services and     System Aspects; System Architecture for the 5G System; Stage 2     (Release 16) -   NPL 2: 3GPP TS 23.502 V16.3.0 (2019 December); 3rd Generation     Partnership Project; Technical Specification Group Services and     System Aspects; Procedures for the 5G System; Stage 2 (Release 16) -   NPL 3: 3GPP TS 24.501 V16.3.0 (2019 December); 3rd Generation     Partnership Project; Technical Specification Group Core Network and     Terminals; Non-Access-Stratum (NAS) protocol for 5G System (5GS);     Stage 3 (Release 16) -   NPL 4: 3GPP TR 23.700-40 V0.2.0 (2019 November); 3rd Generation     Partnership Project; Technical Specification Group Services and     System Aspects; Study on Enhancement of Network Slicing Phase 2     (Release 17)

SUMMARY OF INVENTION Technical Problem

For the 5G System (5GS), a 5G Core Network (5GCN) corresponding to a new core network has been under study in order to provide a wide variety of services.

In addition, for the 5G, a network slice has been defined that corresponds to a logical network providing specific network functions and specific network characteristics for a specific service type or a specific group. For example, the network slice may be a logical network provided for terminals with a low delay function, or may be a logical network provided for sensor terminals used in the Internet of Things (IoT).

In the 3GPP, Enhancement of Network Slicing (eNS) has been under study in order to study further functions associated with network slices. Furthermore, in the 3GPP, as study of phase 2 of eNS, addition of a function for managing the number of UEs allowed for each slice has been under study. However, an implementation method for satisfying the above-described demand is not clear.

The present invention is made in the light of the circumstances as described above, and provides a method of implementing a function for eNS in the 5GS.

Solution to Problem

An aspect of the present invention provides a User Equipment (UE; a terminal apparatus) including a transmission and/or reception unit configured to receive a control message from a control apparatus, and a controller, wherein the control message includes one or multiple pieces of first information, each of the one or multiple pieces of first information includes a first Single Network Slice Selection Assistance information (S-NSSAI), second information, third information, fourth information, and a second S-NSSAI indicating mapped S-NSSAI mapped to the first S-NSSAI, the second information is information indicating a rejection cause of the S-NSSAI, the third information is information indicating a value of a back-off timer, the fourth information is information indicating whether the back-off timer is applied to all PLMNs, and the controller, based on reception of the control message, for each of the one or multiple pieces of first information, adds the first S-NSSAI to first Network Slice Selection Assistance information (NSSAI) associated with the second information and the fourth information, deletes the first S-NSSAI included in the first NSSAI from a second NSSAI, deletes a third S-NSSAI associated with the second S-NSSAI from a third NSSAI based on the fourth information, starts the back-off timer associated with the first S-NNSAI or the second S-NSSAI by using a value indicated by the third information, and applies the back-off timer in a range indicated by the fourth information. An aspect of the present invention provides a User Equipment (UE; a terminal apparatus) including a transmission and/or reception unit configured to transmit a registration request message to a control apparatus, a storage unit configured to store a first NSSAI and a second S-NSSAI mapped to a first S-NSSAI included in the first NSSAI, and a controller, wherein the controller includes the first S-NSSAI in the registration request message, where a back-off timer associated with the first S-NSSAI or the second S-NSSAI is not running. An aspect of the present invention provides a User Equipment (UE; a terminal apparatus) including a transmission and/or reception unit configured to receive a control message from a control apparatus, and a controller, wherein the control message includes one or multiple pieces of first information, each of the one or multiple pieces of first information includes a Single Network Slice Selection Assistance information (S-NSSAI), second information, third information, and fourth information, the second information is information indicating a rejection cause of the S-NSSAI, the third information is information indicating a value of a back-off timer, the fourth information is information indicating whether the back-off timer is applied to a current Public Land Mobile Network (PLMN) or to all PLMNs, and the controller, based on reception of the control message, for each of the one or multiple pieces of first information, adds the S-NSSAI to a Network Slice Selection Assistance information (NSSAI) associated with the second information and the fourth information, starts the back-off timer associated with the S-NSSAI by using a value indicated by the third information, applies the back-off timer in a range indicated by the fourth information, and deletes the S-NSSAI from the NSSAI in a case that the back-off timer expires.

Advantageous Effects of Invention

According to an aspect of the present invention, in the 5GS, eNS can be supported, enabling managing the number of UEs allowed for each slice.

BRIEF DESCRIPTION OF DRAWINGS

FIG. 1 is a diagram illustrating an overview of a mobile communication system (EPS/5GS).

FIG. 2 is a diagram illustrating a detailed configuration of the mobile communication system (EPS/5GS).

FIG. 3 is a diagram illustrating an apparatus configuration of a UE.

FIG. 4 is a diagram illustrating a configuration of an access network apparatus (gNB) in the 5GS.

FIG. 5 is a diagram illustrating a configuration of a core network apparatus (AMF/SMF/UPF) in the 5GS.

FIG. 6 is a diagram illustrating a registration procedure.

DESCRIPTION OF EMBODIMENTS

A preferred embodiment for carrying out the present invention will be described below with reference to the drawings. Note that, as an example, an embodiment of a mobile communication system to which the present invention is applied will be described in the present embodiment.

1. Overview of System

First, FIG. 1 is a diagram illustrating an overview of a mobile communication system 1 used in each embodiment, and FIG. 2 is a diagram illustrating a detailed configuration of the mobile communication system 1.

In the illustration of FIG. 1, the mobile communication system 1 includes a UE_A 10, an access network_A 80, a core network_A 90, a Packet Data Network (PDN)_A 5, an access network_B 120, a core network_B 190, and a Data Network (DN)_A 6.

In the following description, the symbols may be omitted, such as in a UE, an access network_A, a core network_A, a PDN, an access network_B, a core network_B, and a DN, in regard to these apparatuses and functions.

Also, FIG. 2 illustrates apparatuses and functions such as a UE_A 10, an E-UTRAN 80, an MME 40, an SGW 35, a PGW-U 30, a PGW-C 32, a PCRF 60, an HSS 50, a 5G AN 120, an AMF 140, a UPF 130, an SMF 132, a PCF 160, a UDM 150, and an N3IWF 170, and interfaces for connecting these apparatuses and functions to each other.

In the following description, the symbols may be omitted, such as in a UE, an E-UTRAN, an MME, an SGW, a PGW-U, a PGW-C, a PCRF, an HSS, a 5G AN, an AMF, a UPF, an SMF, a PCF, a UDM, and an N3IWF, in regard to these apparatuses and functions.

Note that an Evolved Packet System (EPS) that is a 4G system includes the access network_A and the core network_A and may further include the UE and/or the PDN. A 5G System (5GS) that is a 5G system includes the UE, the access network_B, and the core network_B and may further include the DN.

The UE is an apparatus that can be connected to a network service over 3GPP access (also referred to as a 3GPP access network or a 3GPP AN) and/or non-3GPP access (also referred to as a non-3GPP access network or a non-3GPP AN). The UE may be a terminal apparatus capable of performing radio communication, such as a mobile phone or a smartphone, and may be a terminal apparatus that can be connected to both the EPS and the 5GS. The UE may include a Universal Integrated Circuit Card (UICC) and an Embedded UICC (eUICC). Note that the UE may be referred to as a user equipment or a terminal apparatus.

The access network_A corresponds to an Evolved Universal Terrestrial Radio Access Network (E-UTRAN) and/or a radio LAN access network. In the E-UTRAN, one or more evolved Node Bs (eNBs) 45 are deployed. Note that in the following description, the symbol for the eNB 45 may be omitted such as in an eNB. In a case that there are multiple eNBs, the eNBs are connected to each other via, for example, an X2 interface. In the radio LAN access network, one or more access points are deployed.

The access network_B corresponds to a 5G access network (5G AN). The 5G AN includes an NG Radio Access Network (NG-RAN) and/or a non-3GPP access network. In the NG-RAN, one or more NR NodeBs (gNBs) 122 are deployed. Note that in the following description, the symbol for the gNB 122 may be omitted, such as in an eNB. The gNB is a node that provides a New Radio (NR) user plane and control plane to the UE, and is connected to a 5GCN via the NG interface (including the N2 interface or the N3 interface). In other words, the gNB is a base station apparatus newly designed for the 5GS and has functions different from those of the base station apparatus (eNB) used in the EPS that is a 4G system. In a case that there are multiple gNBs, the gNBs are connected to each other via, for example, an Xn interface.

Also, a non-3GPP access network may be an untrusted non-3GPP access network or a trusted non-3GPP access network. Here, the untrusted non-3GPP access network may be a non-3GPP access network that is an access network in which security management is not performed, such as a public wireless LAN, for example. On the other hand, the trusted non-3GPP access network may be an access network defined by 3GPP and may include a trusted non-3GPP access point (TNAP) and a trusted non-3GPP Gateway function (TNGF).

In the following description, the E-UTRAN and the NG-RAN may be referred to as 3GPP access. The radio LAN access network and the non-3GPP AN may be referred to as non-3GPP access. The nodes deployed in the access network_B may also be collectively referred to as NG-RAN nodes.

In the following description, the access network_A, and/or the access network_B, and/or an apparatus included in the access network_A, and/or an apparatus included in the access network_B may be referred to as an access network or an access network apparatus.

The core network_A corresponds to an Evolved Packet Core (EPC). In the EPC, for example, a Mobility Management Entity (MME), a Serving Gateway (SGW), a Packet Data Network Gateway (PGW)-U, a PGW-C, a Policy and Charging Rules Function (PCRF), a Home Subscriber Server (HSS), and the like are deployed.

The core network_B corresponds to a 5G Core Network (5GCN). In the 5GCN, an Access and Mobility Management Function (AMF), a User Plane Function (UPF), a Session Management Function (SMF), a Policy Control Function (PCF), a Unified Data Management (UDM), and the like are deployed. Here, the 5GCN may be referred to as a 5GC.

In the following description, the core network_A, and/or the core network_B, an apparatus included in the core network_A, and/or an apparatus included in the core network_B may be referred to as a core network, a core network apparatus, or an intra-core network apparatus.

The core network (the core network_A and/or the core network_B) may refer to an IP mobile communication network operated by a mobile communication operator (Mobile Network Operator MNO)) connecting the access network (the access network_A and/or the access network_B) and the PDN and/or the DN, a core network for a mobile communication operator that operates and manages the mobile communication system 1, or a core network for a virtual mobile communication operator and a virtual mobile communication service provider such as a Mobile Virtual Network Operator (MVNO) and a Mobile Virtual Network Enabler (MVNE).

FIG. 1 illustrates a case that the PDN and the DN are the same; however the PDN and the DN may be different. The PDN may be a Data Network (DN) that provides communication services for the UE. Note that the DN may be configured as a packet data service network or may be configured for each service. In addition, the PDN may include a connected communication terminal. Thus, “to be connected to the PDN” may mean “to be connected to a communication terminal and a server apparatus deployed in the PDN”. In addition, “to transmit and/or receive user data to and/or from the PDN” may mean “to transmit and/or receive user data to and/or from a communication terminal and a server apparatus deployed in the PDN”. Note that the PDN may be referred to as a DN, and the DN may be referred to as a PDN.

In the following, at least some of the access network_A, the core network_A, the PDN, the access network_B, the core network_B, and the DN, and/or one or more apparatuses included in these may be referred to as a network or a network apparatus. In other words, the expression that “the network and/or the network apparatus transmits and/or receives a message and/or performs a procedure” means that “at least some of the access network_A, the core network_A, the PDN, the access network_B, the core network_B, and the DN, and/or one or more apparatuses included in these transmit and/or receive a message and/or perform a procedure”.

The UE can be connected to the access network. The UE can be connected to the core network over the access network. In addition, the UE can be connected to the PDN or the DN over the access network and the core network. In other words, the UE can transmit and/or receive (communicate) user data to and/or from the PDN or the DN. In a case that user data is transmitted and/or received, not only Internet Protocol (IP) communication but also non-IP communication may be used.

Here, IP communication refers to data communication using the IP, and data is transmitted and/or received using IP packets. The IP packet includes an IP header and a payload part. In the payload part, data transmitted and/or received by the apparatuses and functions included in the EPS and the apparatuses and functions included in the 5GS may be included. Non-IP communication refers to data communication not using the IP, where data is transmitted and/or received in a form different from the structure of the IP packets. For example, non-IP communication may be data communication implemented through transmission and/or reception of application data to which an IP header is not added, or user data transmitted and/or received by the UE may be transmitted and/or received with another header such as a MAC header and an Ethernet (trade name) frame header added.

Also, apparatuses which are not illustrated in FIG. 2 may be configured in the access network_A, the core network_A, the access network_B, the core network_B, the PDN_A, and the DN_A. For example, the core network_A and/or the core network_B may include an Authentication Server Function (AUSF) and an Authentication, Authorization, and Accounting (AAA) Server (AAA-S).

Here, an AUSF is a core network apparatus provided with an authentication function for 3GPP access and non-3GPP access. Specifically, the AUSF is a network function unit that receives an authentication request for 3GPP access and/or non-3GPP access from the UE and performs an authentication procedure.

Also, the AAA server is an apparatus that is connected directly to the AUSF or indirectly to the AUSF via another network apparatus and has authentication, approval, and billing functions. The AAA server may be a network apparatus within the core network. Note that the AAA server may not be included in the core network_A and/or the core network_B and may be included in the PLMN. In other words, the AAA server may be a core network apparatus or may be an apparatus outside the core network. For example, the AAA server may be a server apparatus within the PLMN managed by a third party.

Note that although each of the apparatuses and functions is illustrated one by one for simplicity in FIG. 2, multiple similar apparatuses and functions may be configured in the mobile communication system 1. Specifically, multiple apparatuses and functions such as the UE_A 10, the E-UTRAN 80, the MME 40, the SGW 35, the PGW-U 30, the PGW-C 32, the PCRF 60, the HSS 50, the 5G AN 120, the AMF 140, the UPF 130, the SMF 132, the PCF 160, and/or the UDM 150 may be configured in the mobile communication system 1.

2. Configuration of Each Apparatus

Next, a configuration of each apparatus (the UE, and/or the access network apparatus, and/or the core network apparatus) used in each embodiment will be described with reference to the drawings. Note that each apparatus may be configured as physical hardware, may be configured as logical (virtual) hardware configured in general-purpose hardware, or may be configured as software. At least a part (including all) of the functions of each apparatus may be configured as physical hardware, logical hardware, or software.

Note that each storage unit (a storage unit_A 340, a storage unit_A 440, a storage unit_B 540, a storage unit_A 640, and a storage unit_B 740) in each apparatus and function to be described later includes, for example, a semiconductor memory, a Solid State Drive (SSD), a Hard Disk Drive (HDD), or the like. Each storage unit can store not only information originally configured at the time of being shipped, but also various pieces of information transmitted and/or received to and/or from apparatuses and functions (for example, the UE, and/or the access network apparatus, and/or the core network apparatus, and/or the PDN, and/or the DN) other than the apparatus and functions of each storage unit. Each storage unit can store identification information, control information, flags, parameters, and the like included in a control message transmitted and/or received in various communication procedures to be described later. Each storage unit may store these pieces of information for each UE. In a case that each storage unit performs interworking between the 5GS and the EPS, each storage unit can store a control message and user data transmitted and/or received to and/or from the apparatuses and functions included in the 5GS and/or the EPS. In this case, not only information transmitted and/or received over the N26 interface but also information transmitted and/or received without using the N26 interface can be stored.

2.1. Apparatus Configuration of UE

First, an apparatus configuration example of the User Equipment (UE) will be described with reference to FIG. 3. The UE includes a controller_A 300, an antenna 310, a transmission and/or reception unit_A 320, and a storage unit_A 340. The controller_A 300, the transmission and/or reception unit_A 320, and the storage unit_A 340 are connected via a bus. The transmission and/or reception unit_A 320 connects to the antenna 310.

The controller_A 300 is a function unit that controls the entire operations and functions of the UE. The controller_A 300 reads and performs various programs stored in the storage unit_A 340 as necessary, and thereby implements various types of processing in the UE.

The transmission and/or reception unit_A 320 is a function unit for performing radio communication with the base station apparatus (the eNB or the gNB) in the access network via the antenna. In other words, with the use of the transmission and/or reception unit_A 320, the UE can transmit and/or receive user data and/or control information to and/or from the access network apparatus, and/or the core network apparatus, and/or the PDN, and/or the DN.

Following is a detailed description with reference to FIG. 2. With the use of the transmission and/or reception unit_A 320, the UE can communicate with the base station apparatus (eNB) in the E-UTRAN over the LTE-Uu interface. The UE can communicate with the base station apparatus (gNB) in the 5G AN with the use of the transmission and/or reception unit_A 320. The UE can transmit and/or receive a Non-Access-Stratum (NAS) message to and/or from the AMF over the N1 interface with the use of the transmission and/or reception unit_A 320. Note that the N1 interface is a logical interface, and thus communication between the UE and the AMF is actually performed over the 5G AN.

The storage unit_A 340 is a function unit for storing programs, user data, control information, and the like necessary for each operation of the UE.

2.2. Apparatus Configuration of gNB

Next, an apparatus configuration example of the gNB will be described with reference to FIG. 4. The gNB includes a controller_B 500, an antenna 510, a network connection unit_B 520, a transmission and/or reception unit_B 530, and a storage unit_B 540. The controller_B 500, the network connection unit_B 520, the transmission and/or reception unit_B 530, and the storage unit_B 540 are connected via a bus. The transmission and/or reception unit_B 530 connects to the antenna 510.

The controller_B 500 is a function unit that controls the entire operations and functions of the gNB. The controller_B 500 reads and performs various programs stored in the storage unit_B 540 as necessary, and thereby implements various types of processing in the gNB.

The network connection unit_B 520 is a function unit for the gNB to communicate with the AMF and/or the UPF. In other words, with the use of the network connection unit_B 520, the gNB can transmit and/or receive user data and/or control information to and/or from the AMF and/or the UPF.

The transmission and/or reception unit_B 530 is a function unit for performing radio communication with the UE via the antenna 510. In other words, with the use of the transmission and/or reception unit_B 530, the gNB can transmit and/or receive user data and/or control information to and/or from the UE.

Following is a detailed description with reference to FIG. 2. With the use of the network connection unit_B 520, the gNB in the 5G AN can communicate with the AMF over the N2 interface and can communicate with the UPF over the N3 interface. The gNB can communicate with the UE with the use of the transmission and/or reception unit_B 530.

The storage unit_B 540 is a function unit for storing programs, user data, control information, and the like necessary for each operation of the gNB.

2.3. Apparatus Configuration of AMF

Next, an apparatus configuration example of the AMF will be described with reference to FIG. 5. The AMF includes a controller_B 700, a network connection unit_B 720, and a storage unit_B 740. The controller_B 700, the network connection unit_B 720, and the storage unit_B 740 are connected via a bus. The AMF may be a node that handles the control plane.

The controller_B 700 is a function unit that controls the entire operations and functions of the AMF. The controller_B 700 reads and performs various programs stored in the storage unit_B 740 as necessary, and thereby implements various types of processing in the AMF.

The network connection unit_B 720 is a function unit for the AMF to connect to the base station apparatus (gNB), and/or the SMF, and/or the PCF, and/or the UDM, and/or the SCEF in the 5G AN. In other words, with the use of the network connection unit_B 720, the AMF can transmit and/or receive user data and/or control information to and/or from the base station apparatus (gNB), and/or the SMF, and/or the PCF, and/or the UDM, and/or the SCEF in the 5G AN.

Following is a detailed description with reference to FIG. 2. With the use of the network connection unit_A 620, the AMF in the 5GCN can communicate with the gNB over the N2 interface, can communicate with the UDM over the N8 interface, can communicate with the SMF over the N11 interface, and can communicate with the PCF over the N15 interface. The AMF can transmit and/or receive a NAS message to and/or from the UE over the N1 interface with the use of the network connection unit_A 620. Note that the N1 interface is a logical interface, and thus communication between the UE and the AMF is actually performed over the 5G AN. In a case that the AMF supports the N26 interface, the AMF can communicate with the MME over the N26 interface with the use of the network connection unit_A 620.

The storage unit_B 740 is a function unit for storing programs, user data, control information, and the like necessary for each operation of the AMF.

Note that the AMF has a function of exchanging a control message with the RAN using the N2 interface, a function of exchanging a NAS message with the UE using the N1 interface, a function of performing encryption and integrity protection of a NAS message, a Registration management (RM) function, a Connection management (CM) function, a Reachability management function, a Mobility management function for the UE or the like, a function of transferring a Session Management (SM) message between the UE and the SMF, an Access Authentication (Access Authorization) function, a security anchor function (Security Anchor Functionality (SEA)), a Security Context Management (SCM) function, a function of supporting the N2 interface for a Non-3GPP Interworking Function (N3IWF), a function of supporting transmission and/or reception of a NAS signal with the UE via the N3IWF, a function of authenticating the UE connected via the N3IWF, and the like.

In registration management, an RM state for each UE is managed. The RM state may be synchronized between the UE and the AMF. The RM state includes a deregistered state (RM-DEREGISTERED state) and a registered state (RM-REGISTERED state). In the RM-DEREGISTERED state, the UE is not registered in the network, and thus the AMF is in a state of being unable to reach the UE, because a UE context in the AMF does not have valid location information and routing information for the UE. In the RM-REGISTERED state, the UE is registered in the network, and thus the UE can receive a service that requires registration in the network. Note that the RM state may be referred to as a 5GMM state. In this case, the RM-DEREGISTERED state may be referred to as a 5GMM-DEREGISTERED state, and the RM-REGISTERED state may be referred to as a 5GMM-REGISTERED state.

In other words, 5GMM-REGISTERED may be a state in which each apparatus establishes a 5GMM context, or may be a state in which each apparatus establishes a PDU session context. Note that, in a case that each apparatus is 5GMM-REGISTERED, the UE_A 10 may start transmission and/or reception of user data and a control message, or may respond to paging. In addition, note that, in a case that each apparatus is 5GMM-REGISTERED, the UE_A 10 may perform a registration procedure other than a registration procedure for initial registration, and/or a service request procedure.

In addition, 5GMM-DEREGISTERED may be a state in which each apparatus does not establish the 5GMM context, may be a state in which the location information of the UE_A 10 is not known to the network, or may be a state in which the network is in a state of being unable to reach the UE_A 10. Note that, in a case that each apparatus is 5GMM-DEREGISTERED, the UE_A 10 may initiate the registration procedure, or may perform the registration procedure to thereby establish the 5GMM context.

In connection management, a CM state for each UE is managed. The CM state may be synchronized between the UE and the AMF. The CM state includes a non-connected state (CM-IDLE state) and a connected state (CM-CONNECTED state). In the CM-IDLE state, the UE is in the RM-REGISTERED state, but does not have NAS signaling connection established with the AMF via the N1 interface. In the CM-IDLE state, the UE does not have connection of the N2 interface (N2 connection) and connection of the N3 interface (N3 connection). In contrast, in the CM-CONNECTED state, the UE has NAS signaling connection established with the AMF via the N1 interface. In the CM-CONNECTED state, the UE may have connection of the N2 interface (N2 connection) and/or connection of the N3 interface (N3 connection).

In addition, in connection management, management may be performed separately for the CM state in 3GPP access and the CM state in non-3GPP access. In this case, the CM state in 3GPP access may include a non-connected state in 3GPP access (CM-IDLE state over 3GPP access) and a connected state in 3GPP access (CM-CONNECTED state over 3GPP access). In addition, the CM state in non-3GPP access may include a non-connected state in non-3GPP access (CM-IDLE state over non-3GPP access) and a connected state in non-3GPP access (CM-CONNECTED state over non-3GPP access). Note that the non-connected state may be referred to as an idle mode, and a connected state mode may be referred to as a connected mode.

Note that the CM state may be referred to as a 5GMM mode. In this case, the non-connected state may be referred to as a 5GMM non-connected mode (5GMM-IDLE mode), and the connected state may be referred to as a 5GMM connected mode (5GMM-CONNECTED mode). In addition, the non-connected state in 3GPP access may be referred to as a 5GMM non-connected mode in 3GPP access (5GMM-IDLE mode over 3GPP access), and the connected state in 3GPP access may be referred to as a 5GMM connected mode in 3GPP access (5GMM-CONNECTED mode over 3GPP access). In addition, the non-connected state in non-3GPP access may be referred to as a 5GMM non-connected mode in non-3GPP access (5GMM-IDLE mode over non-3GPP access), and the connected state in non-3GPP access may be referred to as a 5GMM connected mode in non-3GPP access (5GMM-CONNECTED mode over non-3GPP access). Note that the 5GMM non-connected mode may be referred to as an idle mode, and the 5GMM connected mode may be referred to as a connected mode.

One or more AMFs may be deployed in the core network_B. The AMF may be an NF that manages one or more Network Slice Instances (NSIs). The AMF may be a common CP function (Common Control Plane Network Function (CPNF) (CCNF)) shared among multiple NSIs.

Note that, in a case that the UE connects to the 5GS over non-3GPP access, the N31WF is an apparatus deployed and/or a function allocated between non-3GPP access and the 5GCN.

2.4. Apparatus Configuration of SMF

Next, an apparatus configuration example of the SMF will be described with reference to FIG. 5. The SMF includes a controller_B 700, a network connection unit_B 720, and a storage unit_B 740. The controller_B 700, the network connection unit_B 720, and the storage unit_B 740 are connected via a bus. The SMF may be a node that handles the control plane.

The controller_B 700 is a function unit that controls the entire operations and functions of the SMF. The controller_B 700 reads and performs various programs stored in the storage unit_B 740 as necessary, and thereby implements various types of processing in the SMF.

The network connection unit_B 720 is a function unit for the SMF to connect to the AMF, and/or the UPF, and/or the PCF, and/or the UDM. In other words, with the use of the network connection unit_B 720, the SMF can transmit and/or receive user data and/or control information to and/or from the AMF, and/or the UPF, and/or the PCF, and/or the UDM.

Following is a detailed description with reference to FIG. 2. With the use of the network connection unit_A 620, the SMF in the 5GCN can communicate with the AMF over the N11 interface, can communicate with the UPF over the N4 interface, can communicate with the PCF via the N7 interface, and can communicate with the UDM over the N10 interface.

The storage unit_B 740 is a function unit for storing programs, user data, control information, and the like necessary for each operation of the SMF.

The SMF has a Session Management function such as establishment, modification, and release of a PDU session, a function of IP address allocation to the UE and management thereof, a function of selection and control of the UPF, a function of configuring the UPF for routing traffic to an appropriate destination (transmission destination), a function of transmitting and/or receiving an SM part of a NAS message, a function of issuing a notification about arrival of downlink data (Downlink Data Notification), a function of providing SM information specific to the AN (for each AN) that is transmitted to the AN through the AMF over the N2 interface, a function of determining a Session and Service Continuity mode (SSC mode) for a session, a roaming function, and the like.

2.5. Apparatus Configuration of UPF

Next, an apparatus configuration example of the UPF will be described with reference to FIG. 5. The UPF includes a controller_B 700, a network connection unit_B 720, and a storage unit_B 740. The controller_B 700, the network connection unit_B 720, and the storage unit_B 740 are connected via a bus. The UPF may be a node that handles the control plane.

The controller_B 700 is a function unit that controls the entire operations and functions of the UPF. The controller_B 700 reads and performs various programs stored in the storage unit_B 740 as necessary, and thereby implements various types of processing in the UPF.

The network connection unit_B 720 is a function unit for the UPF to connect to the base station apparatus (gNB), and/or the SMF, and/or the DN in the 5G AN. In other words, with the use of the network connection unit_B 720, the UPF can transmit and/or receive user data and/or control information to and/or from the base station apparatus (gNB), and/or the SMF, and/or the DN in the 5G AN.

Following is a detailed description with reference to FIG. 2. With the use of the network connection unit_A 620, the UPF in the 5GCN can communicate with the gNB over the N3 interface, can communicate with the SMF over the N4 interface, can communicate with the DN over the N6 interface, and can communicate with another UPF over the N9 interface.

The storage unit_B 740 is a function unit for storing programs, user data, control information, and the like necessary for each operation of the UPF.

The UPF has a function as an anchor point for intra-RAT mobility or inter-RAT mobility, a function as an external PDU session point to be mutually connected with the DN (that is, a function of transferring user data as a gateway between the DN and the core network_B), a function of routing and transferring packets, an Uplink Classifier (UL CL) function of supporting routing of multiple traffic flows for one DN, a Branching Point function of supporting a multi-homed PDU session, a Quality of Service (QoS) processing function for the user plane, a function of verifying uplink traffic, a function of triggering buffering of downlink packets and Downlink Data Notification, and the like.

The UPF may be a gateway for IP communication and/or non-IP communication. The UPF may have a function of transferring IP communication or a function of conversion between non-IP communication and IP communication. In addition, multiple deployed gateways may be gateways for connecting the core network_B and a single DN. Note that the UPF may have connectivity with another NF, and may connect to each apparatus via another NF.

Note that the user plane refers to user data that is transmitted and/or received between the UE and the network. The user plane may be transmitted and/or received using a PDN connection or a PDU session. In addition, in a case of the EPS, the user plane may be transmitted and/or received using the LTE-Uu interface, and/or the S1-U interface, and/or the S5 interface, and/or the S8 interface, and/or the SGi interface. In addition, in a case of the 5GS, the user plane may be transmitted and/or received over the interface between the UE and the NG RAN, and/or the N3 interface, and/or the N9 interface, and/or the N6 interface. The user plane may be hereinafter referred to as a U-Plane.

In addition, the control plane refers to a control message that is transmitted and/or received in order to perform communication control of the UE or the like. The control plane may be transmitted and/or received using Non-Access-Stratum (NAS) signaling connection between the UE and the MME. In addition, in a case of the EPS, the control plane may be transmitted and/or received using the LTE-Uu interface and the S1-MME interface. In addition, in a case of the 5GS, the control plane may be transmitted and/or received using the interface between the UE and the NG RAN and the N2 interface. The control plane may be hereinafter referred to as a control plane, or may be hereinafter referred to as a C-Plane.

In addition, the User Plane (U-Plane (UP)) may be a communication path for transmitting and/or receiving user data, and may include multiple bearers. In addition, the Control Plane (C-Plane (CP)) may be a communication path for transmitting and/or receiving a control message, and may include multiple bearers.

2.6. Description of Other Apparatuses and/or Functions and/or Identification Information in Present Embodiment

Now, other apparatuses and/or functions and/or identification information will be described.

A network refers to at least some of the access network_B, the core network_B, and the DN. One or more apparatuses included in at least a part of the access network_B, the core network_B, and the DN may be referred to as a network or a network apparatus. In other words, “a network transmits and/or receives a message and/or performs processing” may mean “an apparatus (a network apparatus and/or a control apparatus) in the network transmits and/or receives the message and/or performs the processing”. Conversely, “an apparatus in a network transmits and/or receives a message and/or performs processing” may mean “the network transmits and/or receives the message and/or performs the processing”.

A session management (SM) message (also referred to as a Non-Access-Stratum (NAS) SM message) may be a NAS message used in a procedure for SM, or may be a control message transmitted and/or received between the UE_A 10 and the SMF_A 230 via the AMF_A 240. Furthermore, the SM message may include a PDU session establishment request message, a PDU session establishment accept message, a PDU session reject message (PDU session establishment reject message), a PDU session modification request message, a PDU session modification command message, a PDU session modification complete message (PDU session modification complete), a PDU session modification command reject message, a PDU session modification reject message, a PDU session release request message, a PDU session release reject message, a PDU session release command message, a PDU session release complete message, and the like. The procedure for SM or the SM procedure may include a PDU session establishment procedure, a PDU session modification procedure, and a PDU session release procedure (UE-requested PDU session release procedure). Note that each procedure may be a procedure initiated by the UE, or may be a procedure initiated by the NW.

A Mobility management (MM) message (also referred to as a NAS MM message) may be a NAS message used in a procedure for MM, or may be a control message transmitted and/or received between the UE_A 10 and the AMF_A 240. Furthermore, the MM message may include a Registration request message, a Registration accept message, a Registration reject message, a De-registration request message, a De-registration accept message, a configuration update command message, a configuration update complete message, a Service request message, a Service accept message, a Service reject message, a Notification message, a Notification response message, and the like. The procedure for MM or the MM procedure may include a Registration procedure, a De-registration procedure, a Generic UE configuration update procedure, an authentication and authorization procedure, a Service request procedure, a Paging procedure, and a Notification procedure.

A 5G System (5GS) service may be a connection service provided using the core network_B 190. In addition, the 5GS service may be a service different from an EPS service, or may be a service similar to the EPS service.

A non 5GS service may be a service other than the 5GS service and may include an EPS service and/or a non EPS service.

A Packet Data Network (PDN) type indicates a type of PDN connection and includes IPv4, IPv6, IPv4v6, and non-IP. In a case that IPv4 is specified, it is indicated that transmission and/or reception of data is performed using IPv4. In a case that IPv6 is specified, it is indicated that transmission and/or reception of data is performed using IPv6. In a case that IPv4v6 is specified, it is indicated that transmission and/or reception of data is performed using IPv4 or IPv6. In a case that non-IP is specified, it is indicated that communication is performed using a communication method other than the IP, not communication using the IP.

Although a Protocol Data Unit/Packet Data Unit (PDU) session can be defined as a relationship between the DN that provides a PDU connectivity service and the UE, the PDU session may be connectivity established between the UE and an external gateway. In the 5GS, the UE establishes a PDU session via the access network_B and the core network_B, and can thereby perform transmission and/or reception of user data to and/or from the DN by using the PDU session. Here, the external gateway may be a UPF, an SCEF, or the like. The UE can perform transmission and/or reception of user data to and/or from an apparatus deployed in the DN, such as an application server, by using a PDU session.

Note that each apparatus (the UE, and/or the access network apparatus, and/or the core network apparatus) may associate one or more pieces of identification information with PDU session(s) for management. Note that these pieces of identification information may include one or more of a DNN, a QoS rule, a PDU session type, application identification information, NSI identification information, access network identification information, and an SSC mode, and may further include other pieces of information. In addition, in a case that multiple PDU sessions are established, pieces of identification information associated with the PDU sessions may have the same or different contents.

The Data Network Name (DNN) may be identification information for identifying the core network and/or an external network such as the DN. In addition, the DNN can also be used as information for selecting a gateway such as the PGW_A 30/UPF_A 235 connecting the core network B 190. In addition, the DNN may correspond to an Access Point Name (APN).

A Protocol Data Unit/Packet Data Unit (PDU) session type indicates a type of PDU session and includes IPv4, IPv6, Ethernet, and Unstructured. In a case that IPv4 is specified, it is indicated that transmission and/or reception of data is performed using IPv4. In a case that IPv6 is specified, it is indicated that transmission and/or reception of data is performed using IPv6. In a case that Ethernet is specified, it is indicated that transmission and/or reception of an Ethernet frame is performed. Alternatively, Ethernet may indicate that communication using the IP is not performed. In a case that Unstructured is specified, it is indicated that data is transmitted and/or received to and/or from an application server in the DN or the like by using a Point-to-Point (P2P) tunneling technique. For the P2P tunneling technique, for example, a UDP/IP encapsulation technique may be used. Note that the PDU session type may include the IP, in addition to the above. The IP can be specified in a case that the UE can use both of IPv4 and IPv6.

The Public Land Mobile Network (PLMN) is a communication network that provides mobile radio communication services. The PLMN is a network managed by an operator who is a network operator, and the operator can be identified by a PLMN ID. A PLMN that matches a Mobile Network Code (MNC) and a Mobile Country Code (MCC) of an International Mobile Subscriber Identity (IMSI) of the UE may be a Home PLMN (HPLMN). Furthermore, the UE may hold, in the USIM, an Equivalent HPLMN list for identifying one or multiple Equivalent HPLMNs (EPLMNs). A PLMN different from the HPLMN and/or the EPLMN may be a VPLMN (Visited PLMN). A PLMN with which the UE has successfully registered may be a Registered PLMN (RPLMN).

A network slice (NS) is a logical network that provides specific network capability and network characteristics. The UE and/or the network can support the network slice (NW slice (NS)) in the 5GS. The network slice may simply be referred to as a slice.

A network slice instance (NSI) includes a set of an instance (entity) of a network function (NF) and necessary resources and forms a network slice to be allocated. Here, the NF is a processing function in a network, and is adopted or defined in 3GPP. The NSI is an entity of one or more NSs configured in the core network_B. The NSI may include a virtual Network Function (NF) generated using a Network Slice Template (NST). Here, the NST is associated with a resource request for provision of a requested communication service and capability, and is a logical expression of one or more NFs. In other words, the NSI may be a set of multiple NFs in the core network_B 190. The NSI may be a logical network configured for classifying user data to be delivered depending on a service or the like. In the NS, one or more NFs may be configured. The NF configured in the NS may or may not be an apparatus shared with another NS. The UE and/or the apparatus in the network can be allocated to one or more NSs, based on an NSSAI, and/or an S-NSSAI, and/or a UE usage type, and/or registration information such as one or more NSI IDs, and/or an APN. Note that the UE usage type is a parameter value included in registration information of the UE, which is used for identifying the NSI. The UE usage type may be stored in the HSS. The AMF may select the SMF and the UPF, based on the UE usage type.

The Single Network Slice Selection Assistance Information (S-NSSAI) is information for identifying the NS. The S-NSSAI may include only a Slice/Service type (SST), or may include both of an SST and a Slice Differentiator (SD). Here, the SST is information indicating operation of the NS expected in terms of functions and services. The SD may be information for interpolating an SST in a case of selecting one NSI out of multiple NSIs indicated by the SST. The S-NSSAI may be information unique to each PLMN or may be standard information common to the PLMNs. The network may store one or more S-NSSAIs in the registration information of the UE as default S-NSSAIs. Note that, in a case that the S-NSSAI is a default S-NSSAI, and the UE does not transmit to a network a valid S-NSSAI in a registration request message, the network may provide an NS related to the UE.

The Network Slice Selection Assistance Information (NSSAI) is a set of S-NSSAIs. Each S-NSSAI included in the NSSAI is information for assisting the access network or the core network to select the NSI. The UE may store the NSSAI allowed by the network for each PLMN. The NSSAI may be information used for selecting the AMF.

Also, configured NSSAI is NSSAI fed and stored in the UE. The UE may store the configured NSSAI for each PLMN. The configured NSSAI may be information configured by the network (or PLMN). The S-NSSAI included in the configured NSSAI may be represented as configured S-NSSAI. The configured S-NSSAI may include S-NSSAI and mapped S-NSSAI.

Requested NSSAI is NSSAI provided to the network from the UE during the registration procedure. The requested NSSAI may be allowed NSSAI or configured NSSAI stored by the UE. Specifically, the requested NSSAI may be information indicating a network slice that the UE is to access. The S-NSSAI included in the requested NSSAI may be represented as requested S-NSSAI. For example, the requested NSSAI is included, for transmission, in an NAS message transmitted from the UE to the network, such as a registration request message or a PDU session establishment request message, or in a Radio Resource Control (RRC) message including the NAS (Non-Access-Stratum) message.

The allowed NSSAI is information indicating one or multiple network slices allowed for the UE. In other words, the allowed NSSAI is information identifying a network slice to which the UE is allowed by the network to connect. The UE and the network each store and manage the allowed NSSAI for each access (3GPP access or non-3GPP access) as UE information. The S-NSSAI included in the allowed NSSAI may be represented as allowed S-NSSAI. The allowed S-NSSAI may include S-NSSAI and mapped S-NSSAI.

The mapped S-NSSAI is the S-NSSAI of the HPLMN mapped to the S-NSSAI of the registered PLMN in a roaming scenario. The UE may store one or multiple pieces of mapped S-NSSAI mapped to the S-NSSAI included in the configured NSSAI and the Allowed NSSAI of each access type. Furthermore, the UE may store one or multiple pieces of mapped S-NSSAI of the S-NSSAI included in the first NSSAI and/or the rejected NSSAI.

Rejected NSSAI is information indicating one or multiple network slices not allowed for the UE. In other words, the rejected NSSAI is information identifying a network slice to which the UE is not allowed by the network to connect. The rejected NSSAI may be information including one or multiple combinations of S-NSSAI and a reject cause value. Here, the reject cause value is information indicating why the network rejects the corresponding S-NSSAI. The UE and the network may each appropriately store and manage the rejected NSSAI based on the reject cause value associated with each S-NSSAI. Furthermore, the rejected NSSAI may be included in the NAS message transmitted from the network to the UE, such as the registration accept message, the configuration update command, the registration reject message, or in the RRC message including the NAS message. The S-NSSAI included in the rejected NSSAI may be represented as rejected S-NSSAI. The rejected NSSAI may be any of the first to third rejected NSSAI, the pending NSSAI, and the first NSSAI, or a combination thereof. The S-NSSAI included in the rejected NSSAI may be represented as rejected S-NSSAI. The rejected S-NSSAI may include the S-NSSAI and the mapped S-NSSAI.

Here, the first rejected NSSAI is a set of one or more pieces of the S-NSSAI included in the requested NSSAI by the UE, the one or more pieces of S-NSSAI being not available in the current PLMN. The first rejected NSSAI may be Rejected NSSAI for the current PLMN in the 5GS, may be Rejected S-NSSAI for the current PLMN, or may be S-NSSAI included in the Rejected NSSAI for the current PLMN. The first rejected NSSAI may be rejected NSSAI stored by the UE or the NW, or may be rejected NSSAI transmitted from the NW to the UE. In a case that the first rejected NSSAI is rejected NSSAI transmitted from the NW to the UE, the first rejected NSSAI may be information including one or multiple combinations of S-NSSAI and a cause value. The reject cause value in this case may be “S-NSSAI is not available in the current PLMN,” or may be information indicating that the S-NSSAI associated with the reject cause value is not available in the current PLMN.

The first rejected NSSAI is valid for the entire registered PLMN. In other words, the UE and/or NW may treat the first rejected NSSAI and the S-NSSAI included in the first rejected NSSAI as information not dependent on the access type. In other words, the first rejected NSSAI may be information valid for 3GPP access and non-3GPP access.

In a case that the UE transitions to a deregistered state on both the 3GPP access and the non-3GPP access for the current PLMN, the UE may delete the first rejected NSSAI from storage. In other words, in a case that the UE transitions to the deregistered state for the current PLMN via one access, or successfully registers with a new PLMN via one certain access, or fails to register with a new PLMN via one access and transitions to the deregistered state, and further that the UE is not registered (deregistered state) via the other access, then the UE deletes the first rejected NSSAI.

The second rejected NSSAI is a set of one or multiple pieces of the S-NSSAI included in the requested NSSAI by the UE, the one or multiple pieces of NSSAI being not available in the current registration area. The second rejected NSSAI may be Rejected NSSAI for the current registration area in the 5GS. The second rejected NSSAI may be rejected NSSAI stored by the UE or the NW, or may be rejected NSSAI transmitted from the NW to the UE. In a case that the second rejected NSSAI is rejected NSSAI transmitted from the NW to the UE, the second rejected NSSAI may be information including one or multiple combinations of S-NSSAI and a cause value. The cause value in this case may be “S-NSSAI is not available in the current registration area,” or may be information indicating that the S-NSSAI associated with the cause value is not available in the current registration area.

The second rejected NSSAI is valid in the current registration area. In other words, the UE and/or the NW may treat the second rejected NSSAI and the S-NSSAI included in the second rejected NSSAI as information for each access type. In other words, the second rejected NSSAI may be valid information for each of the 3GPP access or the non-3GPP access. In other words, once the UE transitions to the deregistered state for one access, the UE may delete the second rejected NSSAI from storage.

The third rejected NSSAI is S-NSSAI requiring Network Slice-Specific Authentication and Authorization, and is a set of one or multiple pieces of S-NSSAI for which the Network Slice-Specific Authentication and Authorization has failed or has been revoked. The third rejected NSSAI may be NSSAI stored by the UE and/or the NW, or may be transmitted from the NW to the UE. In a case that the third rejected NSSAI is transmitted from the NW to the UE, the third rejected NSSAI may be information including one or multiple combinations of S-NSSAI and a reject cause value. The reject cause value in this case may be “S-NSSAI is not available due to the failed or revoked network slice-specific authentication and authorization (S-NSSAI is not available due to the failed or revoked network slice-specific authorization and authentication),” and may be information indicating that the Network slice-specific authentication and authorization for the S-NSSAI associated with the reject cause value has failed or has been revoked.

The third rejected NSSAI is valid for the entire registered PLMN. In other words, the UE and/or the NW may treat the third rejected NSSAI and S-NSSAI included in the third rejected NSSAI as information not dependent on the access type. In other words, the third rejected NSSAI may be valid information for the 3GPP access and the non-3GPP access. The third rejected NSSAI may be NSSAI different from the rejected NSSAI. The third rejected NSSAI may be the first rejected NSSAI.

The third rejected NSSAI is rejected NSSAI for the UE to identify a slice rejected due to the failed or revoked Network Slice-Specific Authentication and Authorization from the core network. Specifically, the UE does not initiate the registration request procedure for the S-NSSAI included in the third rejected NSSAI while storing the third rejected NSSAI. The third rejected NSSAI may be identification information including one or multiple pieces of S-NSSAI received from the core network and associated with the reject cause value indicating a failure in the Network Slice-Specific Authentication and Authorization. The third rejected NSSAI is information not dependent on the access type. Specifically, in a case of storing the third rejected NSSAI, the UE need not attempt to transmit, either on the 3GPP access or on the non-3GPP access, the registration request message including the S-NSSAI included in the third rejected NSSAI. Alternatively, the UE can transmit, based on a UE policy, the registration request message including the S-NSSAI included in the third rejected NSSAI. Alternatively, the UE may delete the third rejected NSSAI based on the UE policy, and transition to a state in which the UE can transmit the registration request message including the S-NSSAI included in the third rejected NSSAI. In other words, in a case of transmitting, based on the UE policy, the registration request message including the S-NSSAI included in the third rejected NSSAI, the UE may delete the S-NSSAI from the third rejected NSSAI.

The first NSSAI is information including one or multiple pieces of S-NSSAI for which the maximum number of UEs for each network slice has been reached. The first NSSAI may be rejected NSSAI, Allowed NSSAI, or Pending NSSAI. The first NSSAI may be NSSAI stored by the UE and/or the NW, or NSSAI transmitted from the NW to the UE.

In a case that the first NSSAI is transmitted from the NW to the UE, the first NSSAI may be information including one or multiple pieces of information including at least one of the S-NSSAI and the mapped S-NSSAI, the cause value, the value of the back-off timer, and the valid range of the value of the back-off timer. The cause value in this case may be “S-NSSAI for which the maximum number of UEs for each network slice has been reached” and may be information indicating that the maximum number of UEs has been reached that can be allowed for the S-NSSAI associated with the reject cause value. Here, the cause value may be the reject cause value included in the Rejected NSSAI, or may be flag information. Furthermore, in this case, the value of the back-off timer may be information indicating the duration for which the UE is prohibited from transmitting the MM message and the SM message using the corresponding S-NSSAI or the S-NSSAI related to the mapped S-NSSAI.

Furthermore, the information indicating the valid range of the value of the back-off timer may be information indicating whether the value of the back-off timer is applied to the current Public Land Mobile Network (PLMN), or is applied to all the PLMNs, or is valid in the current registration area.

The first NSSAI may be valid for the entire registered PLMN, or may be valid for all the PLMNs, or may be valid in the registration area. In a case that the first NSSAI is valid for the entire registered PLMN or for all the PLMNs, then the UE and/or NW may treat the first NSSAI and the S-NSSAI included in the first NSSAI as information not dependent on the access type. In a case that the first NSSAI is valid in the registration area, the UE and/or NW may treat the first NSSAI and the S-NSSAI included in the first NSSAI as information for each access type.

The first NSSAI may be allowed NSSAI, rejected NSSAI, pending NSSAI, or information different from these types of information.

The pending NSSAI is S-NSSAI for the network to require a network slice specific authentication, and is a set of one or multiple pieces of S-NSSAI for which network slice specific authentication is not complete and that is not available in the current PLMN. The pending NSSAI may be Rejected NSSAI due to network slice specific authentication and authorization in the 5GS or may be pending NSSAI. The pending NSSAI may be NSSAI stored by the UE or the NW, or may be NSSAI transmitted from the NW to the UE. Note that the pending NSSAI is not limited to the rejected NSSAI and may be NSSAI independent of the rejected NSSAI. In a case that the pending NSSAI is NSSAI transmitted from the NW to the UE, the pending NSSAI may be information including one or multiple combinations of S-NSSAI and a reject cause value. The reject cause value in this case may be “the S-NSSAI pending for Network slice-specific authentication and authorization (Network slice-specific authentication and authorization is pending for the S-NSSAI),” and may be information indicating that the S-NSSAI associated with the reject cause value is prohibited from being used by the UE or is made pending until the Network slice-specific authentication and authorization for that S-NSSAI is complete.

The pending NSSAI is valid for the entire registered PLMN. In other words, the UE and/or the NW may treat the third rejected NSSAI and the S-NSSAI included in the pending NSSAI as information not dependent on the access type. In other words, the pending NSSAI may be information valid for the 3GPP access and the non-3GPP access. The pending NSSAI may be NSSAI different from the rejected NSSAI. The pending NSSAI may be first rejected NSSAI.

The pending NSSAI is NSSAI including one or multiple pieces of S-NSSAI identifying slices for which the procedure has been made pending by the UE. Specifically, while storing the pending NSSAI, the UE does not initiate the registration request procedure for the S-NSSAI included in the pending NSSAI. In other words, the UE does not use the S-NSSAI included in the pending NSSAI during the registration procedure until the Network Slice-Specific Authentication and Authorization for the S-NSSAI included in the pending NSSAI is complete.

The pending NSSAI is identification information including one or multiple pieces of S-NSSAI received from the core network and associated with the reject cause value indicating the pending state associated with the Network Slice-Specific Authentication and Authorization. The pending NSSAI is information not dependent on the access type. Specifically, in a case of storing the pending NSSAI, the UE attempts to transmit, neither on the 3GPP access nor on the non-3GPP access, the registration request message including the S-NSSAI included in the pending NSSAI.

A tracking area is a single or multiple ranges that can be expressed using the location information of the UE_A 10 managed by the core network. The tracking area may include multiple cells. In addition, the tracking area may be an area in which a control message such as paging is broadcast, or may be an area in which the UE_A 10 can move without performing a handover procedure. In addition, the tracking area may be a routing area, or may be a location area. The tracking area may be any area as long as the area is similar to these. The tracking area may be hereinafter a Tracking Area (TA). The tracking area may be identified by a Tracking Area Identity (TAI) including a Tracking Area Code (TAC) and the PLMN.

The Registration area is a set of one or multiple TAs allocated to the UE by the AMF. Note that while moving within one or multiple TAs included in the registration area, the UE_A 10 may be able to move without transmitting and/or receiving a signal for updating the tracking area. In other words, the registration area may be an information group indicating an area in which the UE_A 10 can move without performing the tracking area update procedure. The registration area may be identified by a TAI list configured by one or multiple TAIs.

A UE ID is information for identifying the UE. Specifically, the UE ID may be a SUbscription Concealed Identifier (SUCI), or a Subscription Permanent Identifier (SUPI), or a Globally Unique Temporary Identifier (GUTI), or an International Mobile Subscriber Identity (IMEI), or an IMEI Software Version (IMEISV), or a Temporary Mobile Subscriber Identity (TMSI), for example. Alternatively, the UE ID may be other information configured by an application or within the network. Moreover, the UE ID may be information for identifying the user.

The Network Slice-Specific Authentication and Authorization function is a function to achieve the network slice-specific authentication and authorization. The network slice-specific authentication and authorization allows the UE to be authenticated and authorized outside the core network, such as in a 3rd Party. A PLMN and network apparatus with the Network Slice-Specific Authentication and Authorization function can perform the Network Slice-Specific Authentication and Authorization procedure on a certain piece of S-NSSAI based on the UE registration information. Furthermore, the UE with the Network Slice-Specific Authentication and Authorization function can manage and store the rejected NSSAI made pending due to the Network Slice-Specific Authentication and Authorization and/or the rejected NSSAI resulting from the failed Network Slice-Specific Authentication and Authorization. In this specification, the Network Slice-Specific Authentication and Authorization may also be referred to as the network slice-specific authentication and authorization procedure or the authentication and authorization procedure.

The S-NSSAI requiring the Network Slice-Specific Authentication and Authorization is the S-NSSAI requiring the Network Slice-Specific Authentication and Authorization and managed by the core network and/or the core network apparatus. The core network and/or the core network apparatus may store the S-NSSAI requiring the Network Slice-Specific Authentication and Authorization by storing the S-NSSAI in association with information indicating whether the Network Slice-Specific Authentication and Authorization is required. The core network and/or the core network apparatus may further store the S-NSSAI requiring the Network Slice-Specific Authentication and Authorization, in association with information indicating whether the Network Slice-Specific Authentication and Authorization is complete, or information indicating that the Network Slice-Specific Authentication and Authorization is complete leading to allowance or success. The core network and/or the core network apparatus may manage the S-NSSAI requiring the Network Slice-Specific Authentication and Authorization, as information not related to the access network.

Management of the maximum number of UEs connected to the slice is to manage the maximum number of UEs that can be registered with the network slice or the S-NSSAI at the same time. Here, the UE registered with the network slice or the S-NSSAI may refer to the inclusion of the S-NSSAI indicating the network slice, in the Allowed NSSAI for storage. An apparatus in a network, the apparatus supporting the function to manage the maximum number of UEs connected to the slice, can store, for each piece of S-NSSAI, information as to whether the management of the maximum number of UEs connected to the slice is required and can further check, during the registration procedure, whether the number of registered UEs has reached a certain specified number corresponding to the maximum number. Furthermore, each apparatus that supports the function to manage the maximum number of UEs connected to the slice may be able to store the first NSSAI. In this specification, the maximum number of UEs connected to the slice may be expressed as the maximum number of UEs connected per slice, or the maximum number of UEs that can be registered with the network slice or S-NSSAI, or the maximum number of UEs, or the specified number.

The back-off timer is a timer for prohibiting the transmission of the MM message performed by the UE and/or the initiation of the procedure using the SM message. The back-off timer is managed and run by the UE. The back-off timer may be associated with the S-NSSAI. For the UE, while the back-off timer associated with the S-NSSAI is valid, transmission of the MM message and/or the SM message using the S-NSSAI may be prohibited, or regulated, or limited. These regulations may be regulations based on congestion control in the 5GS, or may be regulations including regulations based on the congestion control in 5GS.

The back-off timer may be a timer that is started and/or stopped in units of S-NSSAI and/or PLMNs.

Specifically, the back-off timer may be associated with the S-NSSAI, and may be a timer for prohibiting transmission of the MM message and/or SM message using specific S-NSSAI. In other words, the UE may be configured not to transmit the MM message and/or SM message using the specific S-NSSAI during the counting of the timer.

Furthermore, the UE may be configured such that, during the counting of the timer, in a new PLMN, the transmission of the MM message and/or SM message prohibited in the original PLMN is allowed, based on a specific condition described below. Note that the expression of allowance of transmission of the MM message and/or the SM message prohibited in the original PLMN may mean allowance of transmission of the MM message and/or the SM message using the same S-NSSAI as that associated with the back-off timer, and/or the S-NSSAI associated with the same S-NSSAI, and/or the S-NSSAI associated with the mapped S-NSSAI of the same S-NSSAI.

Furthermore, the back-off timer may be a timer for prohibiting transmission of the MM message using specific NSSAI. In other words, the UE may be configured not to transmit the MM message using the specific NSSAI and/or the NSSAI including the specific S-NSSAI during the counting of the timer.

Furthermore, the UE may be configured such that, during the counting of the timer, in a new PLMN, the UE is allowed for transmission of the MM message prohibited in the original PLMN, based on the specific condition described below. Note that the expression of allowance of transmission of the MM message prohibited in the original PLMN may mean allowance of transmission of the MM message using the same NSSAI as that associated with the back-off timer and/or the NSSAI including the same S-NSSAI as that associated with the back-off timer. Furthermore, the expression of allowance of transmission of the MM message prohibited in the original PLMN may mean allowance of transmission of the MM message using the NSSAI including the S-NSSAI associated with the S-NSSAI associated with the back-off timer and/or the NSSAI including the S-NSSAI associated with the mapped S-NSSAI of the S-NSSAI associated with the back-off timer.

The back-off timer may be a timer associated with no NSSAI and used for prohibiting transmission of the MM message using the no NSSAI. In other words, the UE_A 10 may be configured not to transmit the MM message using the no NSSAI during the counting of the timer. Furthermore, the UE_A 10 may be configured such that, during the counting of the timer, in a new PLMN, the UE_A 10 is allowed for transmission of the MM message prohibited in the original PLMN, based on the specific condition described below. Note that the expression of allowance of transmission of the MM message prohibited in the original PLMN may mean allowance of the MM message using the no NSSAI.

Furthermore, the back-off timer may be a timer of 5GMM, and/or a timer of EPS mobility management (EMM). Furthermore, the back-off timer may be a timer T3448, or may be a timer equivalent to the timer T3448. In other words, the back-off timer may be the same as or similar to a timer for regulating communication of user data via the control plane.

Now, description will be given of the identification information transmitted and/or received and stored and managed by apparatuses in the present embodiment.

First identification information is information indicating a network slice with which the UE is to be registered. The first identification information may be information including one or more pieces of S-NSSAI associated with the network slice with which the UE is to be registered. The S-NSSAI included in the first identification information may be S-NSSAI included in the configured NSSAI associated with the current PLMN, or may be S-NSSAI included in the allowed NSSAI associated with the current PLMN. In other words, the first identification information may be S-NSSAI included in the configured NSSAI associated with one or more current PLMNs, or S-NSSAI included in the allowed NSSAI associated with one or more current PLMNs, or a combination of the two configurations described above. More specifically, the allowed NSSAI associated with the current PLMN may be allowed NSSAI associated with the current PLMN and the current access type. Furthermore, the first identification information may be Requested NSSAI in the 5GS.

Note that the S-NSSAI included in the first identification information may be S-NSSAI not included in the rejected NSSAI, and/or the pending NSSAI, and/or the first NSSAI. Furthermore, the S-NSSAI included in the first identification information may be the S-NSSAI for which the back-off timer associated with the S-NSSAI or with the mapped S-NSSAI of the S-NSSAI is not running.

Second identification information may be information indicating that the UE supports a function to manage the maximum number of UEs connected to the slice. Alternatively, the second identification information may be information indicating whether the UE supports the function to manage the maximum number of UEs connected to the slice. The second identification information may be 5GMM capability information. The second identification information may be information indicating that the UE can perform storage.

10th identification information may be information indicating the S-NSSAI for which the maximum number of UEs that can be registered with the network slice or the S-NSSAI has been reached. The 10th identification information may be included in the Allowed NSSAI transmitted from the network, may be included in the Rejected NSSAI transmitted from the network, may be included in the Pending NSSAI transmitted from the network, or may be transmitted from the network as information different from the above-described types of information.

Furthermore, the 10th identification information may be NSSAI. Furthermore, the 10th identification information may be Allowed NSSAI, or may be Rejected NSSAI. Furthermore, the 10th identification information may be a Pending NSSAI, or may be NSSAI different from the above-described types of NSSAI.

The 10th identification information may be the first NSSAI or the S-NSSAI included in the first NSSAI. The 10th identification information may include at least one of 11th to 15th identification information. Specifically, the 10th identification information may include at least one or more pieces of information of the S-NSSAI for which the maximum number of UEs that can be registered with the network slice or the S-NSSAI has been reached, the mapped S-NSSAI of the S-NSSAI, the cause value indicating that the maximum number of UEs that can be registered with the network slice or the S-NSSAI has been reached, the value of the back-off timer indicating the period during which the UE is prohibited from transmitting the registration request message using the S-NSSAI, and information indicating the valid range of the back-off timer.

The 10th identification information may further include at least one or more pieces of information of the cause value indicating that the maximum number of UEs that can be registered with the network slice has been reached, the value of the back-off timer indicating the period during which transmission of the registration request message using the no NSSAI is prohibited, and the information indicating the valid range of the back-off timer. Note that the cause value indicating that the maximum number of UEs that can be registered with the network slice has been reached, the value of the back-off timer indicating the period during which transmission of the registration request message using the no NSSAI is prohibited, and the information indicating the valid range of the back-off timer need not be included in the 10th identification information and may be separately transmitted and/or received. Here, in a case that the 10th identification information is included in the rejected NSSAI, the cause value included in the 10th identification information may be the reject cause value.

The 11th identification information may be information and/or a cause value indicated to the UE by the network and indicating that the maximum number of UEs that can be registered with the network slice or the S-NSSAI has been reached. The 11th identification information may be information and/or a cause value indicating that the use of S-NSSAI is rejected or restricted because the maximum number of UEs connected per slice has been reached. In other words, the 11th identification information is the information and cause value indicating that the use of S-NSSAI is rejected or restricted for the UE by the network because the maximum number of UEs connected per slice has been reached. The 11th identification information may be included in the 10th identification information, and may be associated with the S-NSSAI indicated in the 14th identification information included in the same 10th identification information, and/or the mapped S-NSSAI indicated in the 15th identification information. The 11th identification information may be associated with the different pieces of identification information included in the same 10th identification information. In a case that the 11th identification information is included in the rejected NSSAI, the 11th identification information may be a reject cause value. The 11th identification information may be flag information.

Furthermore, the 11th identification information may be a cause value indicating that the connection to the slice is limited and/or is not allowed. Furthermore, the 11th identification information may be a cause value indicating that registration with the slice is limited and/or is not allowed.

Furthermore, the 11th identification information may be a 5G Mobility Management (5GMM) cause. Furthermore, the 11th identification information may be a 22nd 5GMM cause. Here, the 22nd 5GMM cause may be a cause value indicating a congestion. Furthermore, the 22nd 5GMM cause may be information transmitted to the UE due to congestion in the network.

Furthermore, the 11th identification information may be a 5GMM cause other than the 22nd 5GMM cause. For example, the 11th identification information may be information transmitted to the UE due to congestion of network slices. Furthermore, the 11th identification information may be information transmitted to the UE due to the lack of resources in the network slice. Furthermore, the 11th identification information may be a cause value indicating a failure to provide a requested service due to insufficient resources for the specific slice.

The 12th identification information may be the value of the back-off timer. Specifically, the 12th identification information may be information indicating the period in which the network prohibits the UE from transmitting the MM message using the S-NSSAI indicated in the 14th identification information and/or the 15th identification information included in the same 10 identification information, or transmitting an SM message other than a PDU connection release request message. In other words, the 12th identification information may be information indicating the period in which the network prohibits the UE from transmitting the registration request message using the S-NSSAI indicated in the 14th identification information and/or the 15th identification information included in the same 10 identification information.

The 12th identification information may be included in the 10th identification information, and may be associated with the S-NSSAI indicated in the 14th identification information included in the same 10th identification information, and/or with the mapped S-NSSAI indicated in the 15th identification information. The 12th identification information may be associated with the different pieces of identification information included in the same 10th identification information.

The 13th identification information is information indicating the valid range of the back-off timer. Specifically, the 13th identification information may be information indicating the valid range of the back-off timer counted by the UE, with use of the value of the corresponding back-off timer. More specifically, the 13th identification information may be information indicating that the corresponding back-off timer is applied to the current PLMN or to all the PLMNs. Furthermore, alternatively, the 13th identification information may be information indicating that the back-off timer is applied to the current registration area.

Furthermore, the 13th identification information may be information indicating the range of a regulation, or may be information indicating the range in which the regulation is applied. Note that the regulation may be based on congestion control. More specifically, the regulation may limit the transmission of the MM message performed by the UE. Furthermore, the regulation may be implemented by the back-off timer.

The 13th identification information may be included in the 10th identification information, and in that case, the value of the corresponding back-off timer may be a value indicated by the 12th identification information included in the same 10th identification information. Furthermore, in that case, the 13th identification information may be associated with the different pieces of identification information included in the same 10th identification information.

The 14th identification information is information indicating the S-NSSAI for which the maximum number of UEs that can be registered for each piece of the S-NSSAI has been reached. The 14th identification information may be the S-NSSAI included in the 10th identification information, and may be associated with the mapped S-NSSAI indicated in the 15th identification information included in the same 10th identification information. The 14th identification information may be associated with the different pieces of identification information included in the same 10th identification information. Furthermore, the 14th identification information may be S-NSSAI.

The 15th identification information is the S-NSSAI of the HPLMN associated with the corresponding S-NSSAI. Specifically, in a case that the current PLMN is not the HPLMN, the 15th identification information may be information indicating the S-NSSAI of the HPLMN mapped to the S-NSSAI of the current PLMN.

The 15th identification information may be the mapped S-NSSAI included in the 10th identification information, and may be associated with the S-NSSAI indicated in the 14th identification information included in the same 10th identification information, and in that case, the 15th identification information may be the mapped S-NSSAI of the S-NSSAI indicated in the 14th identification information. The 15th identification information may be associated with the different pieces of identification information included in the same 10th identification information. Furthermore, the 15th identification information may be the mapped S-NSSAI of the S-NSSAI indicated by the 14th identification information.

3.1. Description of Procedures Used in Each Embodiment

Next, procedures used in each embodiment will be described. Note that the procedure used in each embodiment includes the registration procedure. Each procedure will be described below.

Note that, in each embodiment, a case that each of the combinations including the HSS and the UDM, the PCF and the PCRF, the SMF and the PGW-C, and the UPF and the PGW-U is configured to form a single apparatus (that is, the same physical hardware, or the same logical hardware, or the same software) as illustrated in FIG. 2 will be described as an example. However, the details described in the present embodiment can also be applied to a case that each of the combinations is configured to form different apparatuses (that is, different pieces of physical hardware, or different pieces of logical hardware, or different pieces of software). For example, data may be directly transmitted and/or received between these apparatuses, data may be transmitted and/or received over the N26 interface between the AMF and the MME, or data may be transmitted and/or received via the UE.

3.2. Registration Procedure

First, the Registration procedure will be described with reference to FIG. 6. Hereinafter, the present procedure will refer to the registration procedure. The registration procedure is a procedure for registration with the access network_B, and/or the core network_B, and/or the DN as initiated by the UE. In a case that the UE is in a state of not being registered with the network, for example, the UE can perform the present procedure at any timing such as the timing at which the UE is turned on. In other words, the UE can initiate the present procedure at any timing in a case that the UE is in the deregistered state (5GMM-DEREGISTERED state). Each apparatus (in particular, the UE and the AMF) can transition to the registered state (5GMM-REGISTERED state), based on completion of the registration procedure. Note that each registered state may be managed by each apparatus for each access. Specifically, each apparatus may independently manage the registration state (registered state or deregistered state) for the 3GPP access and the registration state for the non-3GPP access.

In addition, the registration procedure may be a procedure for updating position registration information of the UE in the network, and/or periodically giving a notification of the state of the UE from the UE to the network, and/or updating a specific parameter related to the UE in the network.

In a case that the UE performs mobility for crossing a TA, the UE may initiate the registration procedure. In other words, in a case that the UE moves to a TA that is different from the TA indicated in the stored TA list, the UE may initiate the registration procedure. Furthermore, the UE may initiate the present procedure in a case that the running back-off timer or any other timer expires. In addition, the UE may initiate the registration procedure in a case that a context of each apparatus needs to be updated due to disconnection and deactivation of a PDU session. In addition, in a case that there is a change in capability information and/or a preference, related to PDU session establishment, of the UE, the UE may initiate the registration procedure. In addition, the UE may periodically initiate the registration procedure. Furthermore, the UE may initiate the registration procedure based on completion of the UE configuration update procedure, or based on completion of the registration procedure, or based on completion of the PDU session establishment procedure, or based on completion of the PDU session management procedure, or based on information received from the network in each procedure, or based on expiry or stoppage of the back-off timer. Note that these are not restrictive, and the UE can perform the registration procedure at any timing.

Note that the above described procedure for the UE to transition from a state of not being registered with the network to a state of being registered with the network may be considered to be an initial registration procedure or a registration procedure for initial registration, and the registration procedure performed in a state in which the UE is registered with the network may be considered to be a registration procedure for mobility and periodic registration update or a mobility and periodic registration procedure.

The new AMF in FIG. 6 indicates the AMF with which the UE is registered according to the present procedure, and the old AMF in FIG. 6 means the AMF with which the UE has been registered according to a procedure before the present procedure. In a case that the AMF is not changed within the present procedure, no interface or procedure occurs between the old AMF and the new AMF, and the new AMF may be the same apparatus as the old AMF. In the present embodiment, the description of the AMF may mean the new AMF, the old AMF, or both.

First, the UE initiates the registration procedure by transmitting the Registration request message to the new AMF (S600), (S602), and (S604). Specifically, the UE transmits an RRC message including the registration request message to the 5G AN (or the gNB) (S600). Moreover, the registration request message is an NAS message transmitted and/or received over the N1 interface. The RRC message may be a control message transmitted and/or received between the UE and the 5G AN (or the gNB). The NAS message is processed in the NAS layer, and the RRC message is processed in the RRC layer. Note that the NAS layer is a layer higher than the RRC layer.

Here, the UE can include and transmit one or more pieces of identification information of at least the first and the second identification information in the registration request message and/or the RRC message. Furthermore, the UE may include and transmit identification information indicating the type of the present procedure, in the registration request message and/or the RRC message. Here, the identification information indicating the type of the present procedure may be a 5GS registration type IE, and may be information indicating that the present procedure is the registration procedure executed for an initial registration, or for update of registration information associated with movement, or for periodic update of registration information, or for emergency registration.

The UE may include UE capability information in the registration request message to notify the network of the functions supported by the UE. Here, the UE capability information may be 5GMM capability in the 5GS.

The UE may include and transmit these pieces of identification information in control messages different from the above-described ones, for example, control messages from layers lower than the RRC layer (for example, the MAC layer, RLC layer, and PDCP layer). Note that, by transmitting these pieces of identification information, the UE may indicate that the UE supports the functions, or may indicate a request from the UE, or may indicate both. Furthermore, in a case that multiple pieces of identification information are transmitted and/or received, two or more pieces of identification information of these pieces of identification information may be configured as one or more pieces of identification information. Note that information indicating support of each function and information indicating a request for use of each function may be transmitted and/or received as the same piece of identification information, or may be transmitted and/or received as different pieces of identification information.

Note that the UE may select or determine whether to transmit the first and the second identification information to the network based on the UE capability information, and/or the UE policy, and/or the UE state, and/or the user registration information, and/or a context stored in the UE, and/or the like.

The UE may transmit the second identification information in a case that the UE includes a function to manage the maximum number of UEs connected to the slice, or requests at least one piece of S-NSSAI that requires to be managed for management of the maximum number of UEs connected to the slice. By transmitting the second identification information, the UE may notify the network that the UE includes a function to store the first NSSAI.

Furthermore, in a case that the UE includes a Network Slice-Specific Authentication and Authorization (NSSAA) function or requests at least one piece of S-NSSAI that identifies a slice that requires NSSAA, the UE may include and transmit the capability information in the registration request message. By transmitting the capability information, the UE may request the network to treat the UE as a UE with the NSSAA function, and to perform, in the procedure related to the UE, an authentication and authorization procedure based on the NSSAA function.

The UE may store the allowed NSSAI for the requested access to the requested PLMN and/or store the configured NSSAI and rejected NSSAI for the requested PLMN. Furthermore, the UE may also store the mapped S-NSSAI of the S-NSSAI included in each NSSAI.

In a case of storing the allowed NSSAI for the requested access to the requested PLMN and/or storing the configured NSSAI, the UE may transmit the second identification information. The UE may select one or multiple pieces of S-NSSAI from the stored allowed NSSAI and/or configured NSSAI and include and transmit the S-NSSAI in the first identification information. In a case of storing the rejected NSSAI, the UE may transmit the first identification information without including, in the first identification information, the S-NSSAI included in the rejected NSSAI. Furthermore, in a case that the back-off timer associated with certain S-NSSAI is valid, in other words, the back-off timer is running, or until the back-off timer is stopped, the UE may transmit the first identification information without including, in the first identification information, the S-NSSAI or S-NSSAI related to the S-NSSAI. Specifically, in a case that the S-NSSAI with which the back-off timer is associated is the S-NSSAI of the requested PLMN, the UE may transmit the first identification information without including the S-NSSAI in the first identification information in a case that the back-off timer is valid.

The UE may include identification information other than the first and second identification information in the registration request message and/or the RRC message including the registration request message, and may include and transmit, for example, the UE ID and/or the PLMN ID and/or the AMF identification information. Here, the AMF identification information may be information for identifying the AMF or a set of AMFs, for example, a 5GS-Temporary Mobile Subscription Identifier (5G-S-TMSI) or a Globally Unique AMF Identifier (GUAMI).

By including and transmitting an SM message (for example, the PDU session establishment request message) in the registration request message, or by transmitting an SM message (for example, the PDU session establishment request message) together with the registration request message, the UE may initiate the PDU session establishment procedure during the registration procedure.

In a case that the 5G AN (or the gNB) receives the RRC message including the registration request message, then the 5G AN (or the gNB) selects the AMF to transfer the registration request message (S602). Note that the 5G AN (or the gNB) can select the AMF based on one or more pieces of identification information included in the registration request message and/or the RRC message including the registration request message. Specifically, the 5G AN (or the gNB) may select the new AMF corresponding to the transmission destination of the registration request message based on at least one piece of identification information of the first and second identification information.

For example, the 5G AN (or gNB) may select the AMF based on the first identification information. Specifically, the 5G AN (or gNB) may select an AMF included in the network slice identified by the S-NSSAI included in the first identification information or an AMF having connectivity to the network slice.

Furthermore, for example, the 5G AN (or gNB) may select, based on the second identification information, an AMF including a function to manage the maximum number of UEs connected to the slice and/or an AMF having connectivity to a network including the function to manage the maximum number of UEs connected to the slice.

Note that the method of selecting the AMF is not limited to that described above and the 5G AN (or the gNB) may select the AMF based on other conditions. The 5G AN (or the gNB) extracts the registration request message from the received RRC message and transfers the registration request message to the selected new AMF (S604). Note that in a case that at least one piece of identification information of the first and second identification information is not included in the registration request message but in the RRC message, the identification information included in the RRC message may be transferred to the selected AMF together with the registration request message (S604).

In a case of receiving the registration request message, the new AMF can perform first condition fulfillment determination. The first condition fulfillment determination is performed by the network (or the new AMF) to determine whether to accept a request from the UE. In a case that the first condition fulfillment determination is true, the new AMF performs procedural steps from S606 to S612. On the other hand, in a case that the first condition fulfillment determination is false, the new AMF may skip procedural steps from S606 to S608 and perform a procedural step in S610.

Alternatively, the new AMF may perform the first condition fulfillment determination after requesting a UE context from the old AMF and then receiving the UE context from the old AMF (S606 and S608). In that case, the new AMF performs S610 and S612 in a case that the first condition fulfillment determination is true. On the other hand, in a case that the first condition fulfillment determination is false, the new AMF may perform S610.

Note that in this regard, in a case that the first condition fulfillment determination is true, the control message transmitted and received in S610 may be the Registration accept message. In a case that the first condition fulfillment determination is false, the control message transmitted and received in S610 may be the Registration reject message.

Note that the first condition fulfillment determination may be performed based on reception of the registration request message, and/or each piece of identification information included in the registration request message, and/or subscriber information, and/or capability information of the network, and/or an operator policy, and/or a network state, and/or registration information of a user, and/or a context stored in the AMF, and/or the like.

For example, the first condition fulfillment determination may be true in a case that the network allows the request from the UE, and the first condition fulfillment determination may be false in a case that the network does not allow the request from the UE. In a case that a network with which the UE is to be registered and/or an apparatus in the network supports the function requested by the UE, the first condition fulfillment determination may be true, whereas in a case that the network and/or the apparatus does not support the function requested by the UE, the first condition fulfillment determination may be false. In addition, in a case that the transmitted and/or received identification information is allowed, the first condition fulfillment determination may be true, whereas in a case that the transmitted and/or received identification information is not allowed, the first condition fulfillment determination may be false.

In a case that the S-NSSAI included in the requested NSSAI received by the AMF from the UE is information for identifying a slice requiring the Network Slice specific Authentication and Authorization procedure and further that the AMF stores, as a success, the result of the Network Slice specific Authentication and Authorization procedure for the S-NSSAI corresponding to the UE, the first condition fulfillment determination may be true. Alternatively, the first condition fulfillment determination may be false in a case that no S-NSSAI is allowed for the UE and that no Allowed NSSAI is scheduled to be allocated to the UE in the future.

The first condition fulfillment determination may be true in a case that the S-NSSAI included in the requested NSSAI received by the AMF from the UE is information for identifying a slice requiring management of the maximum number of UEs connected to the slice and further that the maximum number of UEs is not reached. Alternatively, in a case that no S-NSSAI is allowed for the UE as well, the first condition fulfillment determination may be true in a case that the Allowed NSSAI is expected to be allocated to the UE in the future.

For the AMF, the first condition fulfillment determination may be true or may be false in a case that no S-NSSAI is allowed for the UE and that the first NSSAI is allocated to the UE.

The new AMF performs the procedural steps in S606 and S608 in a case that the new AMF is different from the AMF indicated in the AMF identification information included in the message received from the UE, and the new AMF does not perform the procedural steps in S606 and S608 in a case that the new AMF is the same as the AMF indicated in the AMF identification information included in the message received from the UE. In other words, the procedural steps in S606 and S608 are performed in a case that the present procedure leads to a change of the AMF, and the procedural steps in S606 and S608 are skipped in a case that the AMF is not changed.

A UE context transfer procedure will be described (S606 and S608). The new AMF transmits a UE context request message to the old AMF by using, as the old AMF, the AMF indicated in the AMF identification information (S606). The old AMF transmits the UE context to the new AMF based on the UE context request message received. The New AMF generates a UE context based on the UE context received.

Here, the UE context transmitted from the new AMF to the old AMF may include the UE ID and the allowed NSSAI. The UE context may include the configured NSSAI and/or rejected NSSAI, the NSSAI and/or pending NSSAI, and/or the first NSSAI. Information as to whether notification to the UE is complete may be linked to the allowed NSSAI, and/or the configured NSSAI, and/or the rejected NSSAI, and/or the pending NSSAI, and/or the first NSSAI included in the UE context, and the S-NSSAI included in each piece of NSSAI.

The UE context may include information of the S-NSSAI requiring the Network Slice-Specific Authentication and Authorization procedure, and/or information indicating to the UE the completion of the Network Slice-Specific Authentication and Authorization procedure and a success in authentication, and/or information indicating a failure in the authentication.

The UE context may include the information of the S-NSSAI requiring management of the maximum number of UEs connected to the slice, and/or information indicating that the maximum number of UEs is reached, and/or information indicating whether the maximum number of UEs connected to the slice is reached.

Note that the information regarding the characteristics of the S-NSSAI may be managed as one piece of information and that specifically, the network may associate with each other and store, for each piece of S-NSSAI, information indicating whether the NSSAA is required, whether the NSSAA is successful, whether the maximum number of UEs connected to the slice requires to be managed, and whether the maximum number of UEs connected to the slice has been reached.

The new AMF transmits a control message to the UE based on the determination of the first condition fulfillment determination and/or on the reception of the UE context from the old AMF (S610). The control message may be the registration accept message, or may be the registration reject message.

The new AMF may include and transmit one or multiple pieces of the 10th identification information in the control message. Alternatively, the new AMF may include and transmit one or more pieces of identification information of at least the 10th to the 15th identification information, in the control message. Note that, by transmitting these pieces of identification information and/or the control message, the AMF may indicate that the network supports the functions, may indicate that the request from the UE is accepted, may indicate that the request from the UE is not allowed, or may indicate information obtained by combining the above-described pieces of information. Furthermore, in a case that multiple pieces of identification information are transmitted and/or received, two or more pieces of identification information of these pieces of identification information may be configured as one or more pieces of identification information. Note that information indicating support of each function and information indicating a request for use of each function may be transmitted and/or received as the same piece of identification information, or may be transmitted and/or received as different pieces of identification information.

The AMF may transmit at least one piece of identification information of the 10th to the 15th identification information in a case that the AMF receives, from the UE, at least one piece of identification information of the first and the second identification information and/or that the UE configuration information is updated after the previous registration procedure.

In a case of receiving the first identification information and/or the second identification information from the UE, the AMF may include and transmit at least one piece of identification information of the 10th to the 15th identification information in the control message.

The AMF may further include and transmit the configured NSSAI, and/or the allowed NSSAI, and/or the rejected NSSAI, and/or the pending NSSAI, in the control message. Note that the 10th to the 15th identification information may be included in the allowed NSSAI, and/or the rejected NSSAI, and/or the pending NSSAI for transmission, or may be transmitted as information different from the above-described pieces of information.

At the time of transmission of the control message, in a case that S-NSSAI to be allowed (allowed NSSAI) for the UE is not available but the NSSAA procedure is to be performed after completion of or in parallel with the present procedure, or that the NSSAA procedure is being performed between the UE and the network, or that the pending NSSAI is included and transmitted in the control message, the AMF may include and transmit an empty value in the allowed NSSAI.

At the time of transmission of the control message, in a case of allowing no S-NSSAI (allowed NSSAI) for the UE but including the 10th identification information in the control message, or notifying the first NSSAI to the UE before the present procedure, then the AMF may include and transmit an empty value in the Allowed NSSAI.

In a case of including, in the control message, the 13th identification information indicating application to all the PLMNs, the AMF may also include the 15th identification information in the control message.

The UE receives, from the network, the control message and/or one or more pieces of information of the 10th to the 15th identification information. In particular, the UE receives, from the new AMF, the control message and/or one or more pieces of information of the 10th to the 15th identification information.

Based on the reception of at least one piece of information of the 10th to the 15th identification information, the UE may recognize the information received. Specifically, since the maximum number of UEs connected per slice has been reached, the UE may recognize a state in which the UE is temporarily prohibited from transmitting the MM message and/or the SM message using the S-NSSAI indicated by the 10th identification information, and/or the S-NSSAI indicated by the 14th identification information, and/or the S-NSSAI related to the mapped S-NSSAI indicated by the 15th identification information. Note that the MM procedure may be the registration request message, and the SM message may be the PDU session establishment request message.

Based on the reception of at least one or more pieces of information of the 10th to the 15th identification information and/or the reception of the control message, the UE may perform the following operation for each piece of the 10th identification information.

The UE may include the S-NSSAI indicated by the 10th identification information, and/or the S-NSSAI indicated by the 14th identification information, and/or the S-NSSAI related to the mapped S-NSSAI indicated by the 15th identification information, in the appropriate first NSSAI for storage. Specifically, the UE may add the S-NSSAI indicated by the 14th identification information received to the first NSSAI associated with information indicated in the 11th identification information and/or the 13th identification information.

Alternatively, the UE may add the mapped S-NSSAI indicated by the 15th identification information received to the first NSSAI, or add the S-NSSAI related to the mapped S-NSSAI indicated by the 15th identification information received to the first NSSAI associated with the current PLMN, or to the first NSSAI associated with the current PLMN and the current access type, or to the first NSSAI(s) associated with the current PLMN and all the access types.

Furthermore, in a case that the S-NSSAI included in the first NSSAI stored by the UE is included in the allowed NSSAI stored by the UE and associated with the PLMN and access type requested by the UE in the present procedure and with other access types, the S-NSSAI may be deleted from the allowed NSSAI.

Furthermore, in a case of receiving the 15th identification information, the UE may store the S-NSSAI indicated by the 15th identification information as the mapped S-NSSAI of the S-NSSAI indicated by the 14th identification information.

In a case that the 13th identification information received is information indicating application to all the PLMNs, then the UE may delete the S-NSSAI associated with the mapped S-NSSAI indicated by the 15th identification information from the allowed NSSAI corresponding to the PLMNs other than the current PLMN.

Based on the reception of the 10th identification information and/or the 11th identification information, and/or the reception of the control message, the UE may recognize that the S-NSSAI indicated in the 10th identification information for which the maximum number of UEs connected per slice has been reached. Here, the S-NSSAI indicated in the 10th identification information may be the S-NSSAI indicated in the 14th identification information and/or the mapped S-NSSAI indicated in the 15th identification information.

Based on the reception of at least one or more pieces of information of the 10th to the 15th identification information and/or the reception of the control message, the UE may use the value of the back-off timer received to start the counting of the back-off timer associated with the S-NSSAI or to start the back-off timer and manage the back-off timer. Here, the value of the back-off timer may be the value of the timer indicated in the 10th identification information and/or the 12th identification information, and the S-NSSAI may be the S-NSSAI indicated in the first identification information, and/or the 10th identification information, and/or the 14th identification information, and/or may be the mapped S-NSSAI indicated in the 15th identification information.

During running of the back-off timer, the UE may be in the state in which the US is prohibited from transmitting the MM message and the SM message using the S-NSSAI associated with the back-off timer, or the mapped S-NSSAI associated with the back-off timer, or the S-NSSAI associated with the mapped S-NSSAI associated with the back-off timer.

Furthermore, in a case of receiving the 13th identification information, the UE may apply the back-off timer according to the valid range indicated in the 13th identification information.

Specifically, in a case that the 13th identification information is information indicating the application within the current PLMN, the UE may apply the back-off timer within the current PLMN. Specifically, in response to a change of the PLMN (PLMN change), the UE need not stop the counting of the back-off timer or the back-off timer, but the regulation by the back-off timer associated with the PLMN before movement may be released. In other words, in a case that the PLMN is changed, the UE maintains the back-off timer, but the regulation on the PLMN before movement may be released.

Alternatively, in response to a change of the PLMN, the UE may stop the counting of the back-off timer associated with the current PLMN or stop the back-off timer. In other words, in a case that the PLMN is changed, the UE may stop the back-off timer and the regulation on the PLMN before movement may be released.

Alternatively, in a case that the 13th identification information is information indicating the application to all the PLMNs, the UE may apply the back-off timer in all the PLMNs. In other words, even in a case that the PLMN is changed, the UE may maintain the back-off timer instead of stopping the back-off timer. In a case that the PLMN is changed while the back-off timer is running, the UE may maintain the state in which the MM message and the SM message are prohibited, the MM message and the SM message using the S-NSSAI of the moving destination PLMN associated with the mapped S-NSSAI of the S-NSSAI with which the back-off timer is associated, or the S-NSSAI of the moving destination PLMN associated with the mapped S-NSSAI, or the mapped S-NSSAI.

Alternatively, in a case that the 13th identification information is information indicating the application in the current registration area, the UE may apply the back-off timer in the current registration area. In other words, in response to moving out of the registration area, the UE may stop the counting of the back-off timer or stop the back-off timer.

Further, the UE may manage, and/or store, the 11th identification information, and/or the first NSSAI associated with the 13th identification information.

Here, in response to the stoppage or expiry of the back-off timer, the limitation may be released and the UE may transition to a state in which the UE can transmit the MM message and the SM message using the S-NSSAI with which the back-off timer is associated, and/or the S-NSSAI related to the mapped S-NSSAI with which the back-off timer is associated, and/or the mapped S-NSSAI with which the back-off timer is associated. In other words, in response to the stoppage or expiry of the back-off timer, the UE may transition to the state in which the UE can transmit the MM message using, for the Requested NSSAI, the S-NSSAI with which the back-off timer is associated, and/or the S-NSSAI related to the mapped S-NSSAI with which the back-off timer is associated, and/or the mapped S-NSSAI with which the back-off timer is associated.

Furthermore, in response to the stoppage or expiry of the back-off timer, the UE may transition to a state in which the UE can transmit the MM message using the NSSAI associated with the back-off timer. In other words, in response to the stoppage or expiry of the back-off timer, the UE may transition to the state in which the UE can transmit the MM message using, for the Requested NSSAI, the NSSAI associated with the back-off timer.

Furthermore, in response to the stoppage or expiry of the back-off timer, the UE may delete, from the first NSSAI, the S-NSSAI with which the back-off timer is associated, the mapped S-NSSAI with which the back-off timer is associated, or the S-NSSAI associated with the mapped S-NSSAI with which the back-off timer is associated.

Note that each type of processing performed by the UE based on reception of each piece of identification information described above may be performed during the present procedure or after completion of the present procedure or may be performed based on completion of the present procedure after completion of the present procedure.

Note that the AMF may select and determine at least which piece of identification information out of the 10th to the 15th identification information is to be included in the control message, based on each piece of received identification information, and/or subscriber information, and/or capability information of the network, and/or an operator policy, and/or a state of the network, and/or registration information of a user, and/or a context stored in the AMF, and/or the like.

In a case that the control message is the registration accept message, the AMF can either include and transmit an SM message (for example, the PDU session establishment accept message) in the registration accept message, or transmit an SM message (for example, the PDU session establishment accept message) together with the registration accept message. Note that, such a transmission method may be performed in a case that the SM message (for example, the PDU session establishment request message) is included in the registration request message. The transmission method may be performed in a case that the SM message (for example, the PDU session establishment request message) is transmitted along with the registration request message. By performing such a transmission method as described above, the AMF can indicate that a procedure for SM is accepted in the registration procedure.

By transmitting the registration accept message based on each piece of received identification information, and/or subscriber information, and/or capability information of the network, and/or the operator policy, and/or the state of the network, and/or the registration information of the user, and/or the context stored in the AMF, and/or the like, the AMF may indicate that the request from the UE is accepted, or by transmitting the registration reject message, the AMF may indicate that the request from the UE is rejected.

The UE receives the control message via the 5G AN (gNB) (S608). In a case that the control message is the registration accept message, then by receiving the registration accept message, the UE can recognize that the request from the UE on the registration request message is accepted, and recognize contents of various pieces of identification information included in the registration accept message. Alternatively, in a case that the control message is the registration reject message, then by receiving the registration reject message, the UE can recognize that the request from the UE using the registration request message has been rejected and the content of various pieces of identification information included in the registration reject message. In a case that the UE does not receive the control message even after a prescribed time period has elapsed after transmitting the registration request message, the UE may recognize that the request from the UE is rejected.

Furthermore, in a case that the control message is the registration accept message, the UE can further transmit to the AMF a registration complete message as a response message to the registration accept message via the 5G AN (gNB) (S610). Note that, in a case that the UE receives the SM message such as the PDU session establishment accept message, the UE may include and transmit the SM message such as the PDU session establishment complete message in the registration complete message, or may indicate that the procedure for SM has completed by including the SM message. Here, the registration complete message is a NAS message transmitted and/or received over the N1 interface; however, between the UE and the 5G AN (gNB), the registration complete message is transmitted and/or received in an RRC message.

The AMF receives the registration complete message via the 5G AN (gNB) (S612). Each apparatus completes the present procedure based on transmission and/or reception of the registration accept message and/or the registration complete message.

Alternatively, each apparatus may complete the registration procedure based on the transmission and/or the reception of the registration reject message.

Note that each apparatus may transition to or maintain a state in which the UE is registered with the network (an RM_REGISTERED state or a 5GMM-REGISTERED state) based on the transmission and/or reception of the registration accept message and/or the registration complete message or may transition to or maintain a state in which the UE is not registered with the network (an RM_DEREGISTERED state or a 5GMM-DEREGISTERED state) over the access in which the UE has received the registration reject message for the current PLMN based on the transmission and/or reception of the registration reject message. The transition of each apparatus to each state may be performed based on transmission and/or reception of the registration complete message and completion of the registration procedure.

In addition, each apparatus may perform processing based on information transmitted and/or received in the registration procedure based on completion of the registration procedure. For example, in a case that information indicating that a part of the request from the UE is rejected is transmitted and/or received, a reason of rejection of the request from the UE may be recognized. In addition, each apparatus may perform the present procedure again or may perform the registration procedure on the core network_A or another cell based on the cause for the rejection of the request from the UE.

Moreover, the UE may store the identification information received along with the registration accept message and/or the registration reject message or may recognize determination of the network, based on the completion of the registration procedure.

Furthermore, each apparatus may initiate the registration procedure again based on the expiry or stoppage of the back-off timer.

4. Embodiments in Present Invention

Embodiments in the present invention may be a combination of one or more procedures described in Chapter 3. For example, in the present embodiment described in Chapter 3, one or more movement and periodic registration procedures may be performed after completion of the initial registration procedure.

Specifically, after the completion of the initial procedure, the MM message or the SM message using the S-NSSAI associated with the back-off timer may be transmitted by the UE based on the expiry or stoppage of the back-off timer. Note that, before and after completion of the initial registration procedure or in parallel with the completion, one or multiple MM procedures or SM procedures may be performed.

5. Modified Examples

A program running on an apparatus according to the present invention may serve as a program that controls a Central Processing Unit (CPU) and the like to cause a computer to operate in such a manner as to realize the functions of the aforementioned embodiment according to the present invention. Programs or information handled by the programs are temporarily stored in a volatile memory such as a Random Access Memory (RAM), a non-volatile memory such as a flash memory, a Hard Disk Drive (HDD), or another storage device system.

Note that a program for realizing the functions of the embodiments according to the present invention may be recorded on a computer-readable recording medium. The functions may be realized by causing a computer system to read the program recorded on the recording medium for execution. It is assumed that the “computer system” refers to a computer system built into the apparatuses, and the computer system includes an operating system and hardware components such as a peripheral device. Furthermore, the “computer-readable recording medium” may be any of a semiconductor recording medium, an optical recording medium, a magnetic recording medium, a medium dynamically retaining the program for a short time, or any other computer readable recording medium.

Furthermore, each functional block or various features of the apparatuses used in the aforementioned embodiment may be implemented or performed on an electric circuit, for example, an integrated circuit or multiple integrated circuits. An electric circuit designed to perform the functions described in the present specification may include a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), or other programmable logic devices, discrete gates or transistor logic, discrete hardware components, or a combination thereof. The general-purpose processor may be a microprocessor, or may be a processor of a known type, a controller, a micro-controller, or a state machine instead. The aforementioned electric circuit may include a digital circuit or may include an analog circuit. In a case that with advances in semiconductor technology, a circuit integration technology appears that replaces the present integrated circuits, it is also possible for one or multiple aspects of the present invention to use a new integrated circuit based on the technology.

Note that the invention of the present application is not limited to the above-described embodiments. In the embodiment, apparatuses have been described as an example, but the invention of the present application is not limited to these apparatuses, and is applicable to a terminal apparatus or a communication apparatus of a fixed-type or a stationary-type electronic apparatus installed indoors or outdoors, for example, an AV apparatus, a kitchen apparatus, a cleaning or washing machine, an air-conditioning apparatus, office equipment, a vending machine, and other household apparatuses.

Although, the embodiments of the present invention have been described in detail above referring to the drawings, the specific configuration is not limited to the embodiments and includes, for example, design changes within the scope that does not depart from the gist of the present invention. Furthermore, in the present invention, various modifications are possible within the scope of claims, and embodiments that are made by suitably combining technical means disclosed according to the different embodiments are also included in the technical scope of the present invention. Furthermore, a configuration in which elements described in the respective embodiments and having mutually the same effects, are substituted for one another is also included.

REFERENCE SIGNS LIST

-   1 Mobile communication system -   10 UE_A -   30 PGW-U -   32 PGW-C -   35 SGW -   40 MME -   45 eNB -   50 HSS -   60 PCRF -   80 Access network_A (E-UTRAN) -   90 Core network_A -   120 Access network_B (5G AN) -   122 gNB -   130 UPF -   132 SMF -   140 AMF -   150 UDM -   160 PCF -   190 Core network_B 

1-3. (canceled)
 4. A User Equipment (UE) comprising: transmission and reception circuitry; control circuitry; and storage, wherein the transmission and reception circuitry is configured to: send a registration request message including requested Network Slice Selection Assistance Information (NSSAI) including a Single Network Slice Selection Assistance Information (S-NSSAI); and receive a registration accept message including the S-NSSAI and a cause value indicating that the S-NSSAI is not available due to maximum number of UEs reached, and the controller circuitry adds the S-NSSAI in the rejected NSSAI regarding the S-NSSAI for which the maximum number of UEs has been reached of the storage.
 5. A communication method performed by a User Equipment (UE), the communication method comprising: sending a registration request message including requested Network Slice Selection Assistance Information (NSSAI) including a Single Network Slice Selection Assistance Information (S-NSSAI); receiving a registration accept message including the S-NSSAI and a cause value indicating that the S-NSSAI is not available due to maximum number of UEs reached; and adding the S-NSSAI in the rejected NSSAI regarding the S-NSSAI for which the maximum number of UEs has been reached of the storage. 